Application-level network queueing

ABSTRACT

There is disclosed in one example a network interface card (NIC), comprising: an ingress interface to receive incoming traffic; a plurality of queues to queue incoming traffic; an egress interface to direct incoming traffic to a plurality of server applications; and a queuing engine, including logic to: uniquely associate a queue with a selected server application; receive an incoming network packet; determine that the selected server application may process the incoming network packet; and assign the incoming network packet to the queue.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Non-Provisional applicationSer. No. 14/998,138 filed 26 Dec. 2015, titled “Application-LevelNetwork Queueing.” The above related application is incorporated hereinby reference in its entirety.

FIELD OF THE SPECIFICATION

This disclosure relates in general to the field of computer networking,and more particularly, though not exclusively to, a system and methodfor application-level network queueing.

BACKGROUND

Busy polling, also known as “busy waiting” or “spinning,” is a techniquein which a process repeatedly monitors a condition to see if it hasbecome true. For example, if the process needs input, it may continuallyloop, watching an input buffer to see if data have become available.Other uses may be to see if a key has been pressed, or if a lock isavailable. Another use is to create a known time delay, such as by“doing nothing” for a specified number of milliseconds, thoughvariations in processor speed may make this not completely reliable.

Busy polling may be a useful technique particularly in low-levelprogramming, where interrupt-driven processing may be inefficient orcumbersome.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is best understood from the following detaileddescription when read with the accompanying figures. It is emphasizedthat, in accordance with the standard practice in the industry, variousfeatures are not necessarily drawn to scale, and are used forillustration purposes only. Where a scale is shown, explicitly orimplicitly, it provides only one illustrative example. In otherembodiments, the dimensions of the various features may be arbitrarilyincreased or reduced for clarity of discussion.

FIG. 1 is a block diagram of a security-enabled network according to oneor more examples of the present specification.

FIG. 2 is a block diagram of a client device according to one or moreexamples of the present specification.

FIG. 3 is a block diagram of a server device according to one or moreexamples of the present specification.

FIG. 4 is a block diagram of a network queueing system according to oneor more examples of the present specification.

FIG. 5 is a block diagram of a network queueing system according to oneor more examples of the present specification.

FIG. 6 is a block diagram of an Open Systems Interconnection model (OSI)seven-layer stack according to one or more examples of the presentspecification.

FIG. 7 is a flow chart of a method performed by a network deviceaccording to one or more examples of the present specification.

FIG. 8 is a flow chart of a method performed by an application accordingto one or more examples of the present specification

FIG. 9 is a flow chart of a method performed by an application accordingto one or more examples of the present specification.

FIG. 10 is a flow chart of a transmit operation according to one or moreexamples of the present specification.

SUMMARY

In an example, there is disclosed a network interface card (NIC),comprising: an ingress interface to receive incoming traffic; aplurality of queues to queue incoming traffic; an egress interface todirect incoming traffic to a plurality of server applications; and aqueuing engine, including logic to: uniquely associate a queue with aselected server application; receive an incoming network packet;determine that the selected server application may process the incomingnetwork packet; and assign the incoming network packet to the queue.

Embodiments of the Disclosure

The following disclosure provides many different embodiments, orexamples, for implementing different features of the present disclosure.Specific examples of components and arrangements are described below tosimplify the present disclosure. These are, of course, merely examplesand are not intended to be limiting. Further, the present disclosure mayrepeat reference numerals and/or letters in the various examples. Thisrepetition is for the purpose of simplicity and clarity and does not initself dictate a relationship between the various embodiments and/orconfigurations discussed. Different embodiments may have differentadvantages, and no particular advantage is necessarily required of anyembodiment.

By way of example, modern day data center tiers may include web serversand data caching servers, with “Big Data” backends like the “Hadoop”software framework. These may be networked using leaf spinearchitectures. In one example, these tiers are distributed systems inand of themselves and typically service many thousands of concurrentconnections, with the number of connections expected to increase in thefuture as the number of cores on the end nodes increase.

Some data centers may have a target performance determinism, such as tomeet contractual requirements or as a competitive differentiator.Providing the desired performance determinism (e.g., 99.99 percentilelatency, with consistent throughput and CPU utilization) for distributedsystems applications in this environment may be a challenge. In manycases, the networking interface is one of the primary contributors tothis issue, as it can become a bottleneck to application performance ona busy, high-end server.

This specification describes a system and method for application-levelnetwork queuing (ALNQ), which address network interface bottleneck in ascalable manner. In an embodiment of ALNQ, an improved network interfacecard (NIC) is provided, and adjustments may also be made to the existingnetwork stack, such as the Open Systems Interconnection (OSI) ortransmission control protocol/internet protocol (TCP/IP) stack.Alternatively, in some embodiments, the host network stack is bypassedin whole or in part, and parallel offloaded or onloaded stacks may berun.

Many NICs divide incoming traffic into a plurality of separate “queues,”with traffic being load balanced to queues based on, for example, ahashing algorithm based on a socket tuple that includes the source mediaaccess control address (MAC), destination MAC, and/or protocol. ALNQaddresses issues, such as that applications may desire to have their own“visible” queues and load balancing control using the operating system'snetworking stack. ALNQ makes this possible by creating scalableapplication specific queues on NICs with socket layer visibility and anaffinitization and wakeup algorithm applied to kernel event multiplexinginterfaces like “EPOLL” and “KQUEUE.” In selected embodiments, thisleads to lower and deterministic average and tail latencies, and, higherthroughput within latency tolerance boundaries, which may help inscaling distributed systems.

In an embodiment, ALNQ takes a top-down view with respect to steeringtraffic to an application and delivering low latency communication.Applications, from a networking perspective, may distinguish themselveswithin a system by virtue of a port number. For example, an HTTP daemonmay listen on port 80, while an e-mail daemon may listen on port 25.ALNQ may use the port number (along with other relevant identifyinginformation) as the primary key for assigning traffic to a queue, i.e.application specific queues. Traffic into these queues may bemultiplexed via existing schemes like “Receive Side Scaling” (RSS) forhash-based load balancing, or Intel® Ethernet Flow Director fordeterminate matching.

Information about the assigned queue may be passed up to the applicationas an opaque identifier. The application may then use this identifierfor alignment hints. For example, an application that uses EPOLL mayalign application thread handling the file descriptors to the queue,thus streamlining access and mitigating effects from cache line bouncingof socket and protocol related data structures. Interrupts may also betuned to better match application behavior, as these queues can bedistributed between applications, rather than between cores, which maycause them to be shared between applications. Thus, low latency as anattribute can be applied to an entire application, and therefore a queueset, rather than for a socket (or flow) that is open. This separationalso allows for direct application signaling schemes for wakeup beforeprotocol processing is performed.

Advantageously, ALNQ steers NIC traffic by assigning queues not perinterface or virtual socket interface (VSI), or by VMs or trafficclasses, but rather per port number, with the port number functioning asan application identifier. From a networking perspective, a port numbermay operate as a useful primitive for identifying an application on aparticular machine. Note that the application identifier could be anysuitable application identifier other than the port number.

Further advantageously, ALNQ can load balance the queues assigned to anapplication/port number using known hash-based schemes like RSS or exactmatch schemes like Flow Director

Further advantageously, ALNQ may pass queue information as a token tothe application, such as via an enhancement to the sockets interfaceoptions.

Further advantageously, applications may align threads to queues usingthese tokens.

Further advantageously, separating application-specific traffic earlyprovides a range of affinitization choices, such as using existinglow-latency methods such as Busy Poll Sockets (BPS), providing scalablealigning of queues to application threads, or applying quality ofservice or security policies.

Further advantageously, ALNQ enables an interrupt signaling schemewherein interrupts signal a sleeping application thread directly, whichmay then pull data out from device queues.

A system and method for application level network queueing will now bedescribed with more particular reference to the attached FIGURES. Itshould be noted that throughout the FIGURES, certain reference numeralsmay be repeated to indicate that a particular device or block is whollyor substantially consistent across the FIGURES. This is not, however,intended to imply any particular relationship between the variousembodiments disclosed. In certain examples, a genus of elements may bereferred to by a particular reference numeral (“widget 10”), whileindividual species or examples of the genus may be referred to by ahyphenated numeral (“first specific widget 10-1” and “second specificwidget 10-2”).

FIG. 1 is a network-level diagram of a secured enterprise 100 accordingto one or more examples of the present specification. In this example,secured enterprise 100 may be configured to provide services or data toone or more customers 162, who may access information or services viaexternal network 172. This may require secured enterprise 100 to atleast partly expose certain services and networks to the outside world,thus creating a logical security aperture.

Within secured enterprise, one or more users 120 operate one or moreclient devices 110. Each device may include an appropriate operatingsystem, such as Microsoft Windows, Linux, Android, Mac OSX, Apple iOS,Unix, or similar. Some of the foregoing may be more often used on onetype of device than another. For example, desktop computers orengineering workstation may be more likely to use one of MicrosoftWindows, Linux, Unix, or Mac OSX. Laptop computers, which are usually aportable off-the-shelf device with fewer customization options, may bemore likely to run Microsoft Windows or Mac OSX. Mobile devices may bemore likely to run Android or iOS. However, these examples are notintended to be limiting.

Client devices 110 may be communicatively coupled to one another and toother network resources via enterprise network 170. Enterprise network170 may be any suitable network or combination of one or more networksoperating on one or more suitable networking protocols, including forexample, a local area network, an intranet, a virtual network, a widearea network, a wireless network, a cellular network, or the Internet(optionally accessed via a proxy, virtual machine, or other similarsecurity mechanism) by way of nonlimiting example. Enterprise network170 may also include one or more servers, firewalls, routers, switches,security appliances, antivirus servers, or other useful network devices,which in an example may be virtualized within workload cluster 142. Inthis illustration, enterprise network 170 is shown as a single networkfor simplicity, but in some embodiments, enterprise network 170 mayinclude a large number of networks, such as one or more enterpriseintranets connected to the internet. Enterprise network 170 may alsoprovide access to an external network, such as the Internet, viaexternal network 172. External network 172 may similarly be any suitabletype of network.

A workload cluster 142 may be provided, for example as a virtual clusterrunning in a hypervisor on a plurality of rack-mounted blade servers, oras a cluster of physical servers. Workload cluster 142 may provide oneor more server functions, or one or more “microclouds” in one or morehypervisors. For example, a virtualization environment such as vCentermay provide the ability to define a plurality of “tenants,” with eachtenant being functionally separate from each other tenant, and eachtenant operating as a single-purpose microcloud. Each microcloud mayserve a distinctive function, and may include a plurality of virtualmachines (VMs) of many different flavors, including agentful andagentless VMs.

It should be noted that some functionality of endpoint devices 110 mayalso be provided via workload cluster 142. For example, one microcloudmay provide a remote desktop hypervisor such as a Citrix workspace,which allows users 120 operating endpoints 110 to remotely login to aremote enterprise desktop and access enterprise applications,workspaces, and data. In that case, endpoint 110 could be a “thinclient” such as a Google Chromebook, running only a stripped-downoperating system, and still provide user 120 useful access to enterpriseresources.

One or more computing devices configured as a management console 140 mayalso operate on enterprise network 170. Management console 140 mayprovide a user interface for a security administrator 150 to defineenterprise security policies, which management console 140 may enforceon enterprise network 170 and across client devices 110 and workloadcluster 142. In an example, management console 140 may run aserver-class operating system, such as Linux, Unix, or Windows Server.In other case, management console 140 may be provided as a webinterface, on a desktop-class machine, or via a VM provisioned withinworkload cluster 142.

Secured enterprise 100 may communicate across enterprise boundary 104with external network 172. Enterprise boundary 104 may represent aphysical, logical, or other boundary. External network 172 may include,for example, websites, servers, network protocols, and othernetwork-based services. In another example, secured enterprise 100 maysimply be a family, with parents assuming the role of securityadministrator 150. The parents may wish to protect their children fromundesirable content, such as pornography, adware, spyware,age-inappropriate content, advocacy for certain political, religious, orsocial movements, or forums for discussing illegal or dangerousactivities, by way of non-limiting example. In this case, the parent mayperform some or all of the duties of security administrator 150.

Workload cluster 142 may be configured to provide any suitable networkservices to client devices, such as client device 110 and end userdevice 180. For example, workload cluster 142 may be a rack-mount cloudsystem providing security and infrastructure services such as afirewall, antivirus, deep packet inspection, load balancing, andswitching by way of nonlimiting example. Workload cluster 142 may alsoprovide substantive network services, such as a corporate file server,database file system, intranet server, or a database server by way ofnonlimiting example. An enterprise user 120 may use a client application112 on client device 110 to access services on workload cluster 142 viaenterprise network 170.

End user 160 may also access network resources. End user 160 may operatean end user application 162 on end user device 180, and access workloadcluster 142 via external network 172 and enterprise network 170. Inaccordance with good corporate security practice, network from outsideof secured enterprise 100 may be segregated from corporate networktraffic, such as by placing enterprise traffic and external traffic ondifferent subnetworks.

Workload cluster 142 may provide to external end users 160 varioussuitable network services, such as a website over hypertext transferprotocol (HTTP), e-mail over simple mail transport protocol (SMTP), filesharing via file transfer protocol (FTP), secure FTP (SFTP), or virtualshells via protocols such as telnet or secure shell (SSH).

Note that while end user 160 and corporate user 120 are disclosed hereas two separate entities by way of nonlimiting example, strictsegregation is not required. An end user 160 may also be a corporateuser, and may access corporate resources via a remote client such asCitrix or a remote desktop protocol (RDP). Corporate user 120 may alsobe a guest user with less than full access to enterprise resources.

To provide a simplified example by way of illustration, thisspecification will assume that workload cluster 142 is a single workloadserver 142 having one or more network interface cards (NICs). However,the methods disclosed herein can be scaled to any appropriate number ofservers configured in any appropriate manner, such as standaloneservers, service appliances, individual servers operating multipleprotocols, or a plurality of virtual servers operating on one or aplurality of physical devices.

In this example, workload server 142 hosts both an HTTP web serverreceiving traffic on port 80, and an SMTP mail server receiving trafficon port 25. Workload server 142 may open a unique communication “socket”or other logical connection for each connection with a client device.Thus, for example, if 100,000 users, either corporate users 120 or endusers 160, or any combination thereof, are accessing a website at agiven time, then 100,000 HTTP sockets will be open on port 80.Similarly, if 50,000 e-mail users are accessing e-mail services, then50,000 SMTP sockets will be open on port 25. These quantities areprovided for illustration only. Smaller or independent servers may havefar fewer simultaneous sockets open, while large, popular web servicesmay have many more sockets open.

As illustrated in this specification, with a large number of concurrentconnections, queueing can be a substantial challenge. Certainembodiments of traditional “bottom-up” hash-based queueing such as RSS,in which a packet is hashed starting with the lower levels of the OSInetwork model, may result in substantial latency due to traffic fromother applications sharing the same queues. Thus, this specificationprovides a system and method for providing application-level networkqueuing to reduce latency and improve performance. Example logicalembodiments are illustrated in FIGS. 4 and 5, while example methods areillustrated in FIGS. 7-9.

FIG. 2 is a block diagram of client device 200 according to one or moreexamples of the present specification. Client device 200 may be anysuitable computing device. In various embodiments, a “computing device”may be or comprise, by way of non-limiting example, a computer,workstation, server, mainframe, virtual machine (whether emulated or ona “bare-metal” hypervisor), embedded computer, embedded controller,embedded sensor, personal digital assistant, laptop computer, cellulartelephone, IP telephone, smart phone, tablet computer, convertibletablet computer, computing appliance, network appliance, receiver,wearable computer, handheld calculator, or any other electronic,microelectronic, or microelectromechanical device or apparatus forprocessing and communicating data. Any computing device may bedesignated as a host on the network. Each computing device may refer toitself as a “local host,” while any computing device external to it maybe designated as a “remote host.”

In certain embodiments, client devices 110 may all be examples of clientdevices 200.

Client device 200 includes a processor 210 connected to a memory 220,having stored therein executable instructions for providing an operatingsystem 222 and at least software portions of a client agent 224. Othercomponents of client device 200 include a storage 250, network interface260, and peripheral interface 240. This architecture is provided by wayof example only, and is intended to be non-exclusive and non-limiting.Furthermore, the various parts disclosed are intended to be logicaldivisions only, and need not necessarily represent physically separatehardware and/or software components. Certain computing devices providemain memory 220 and storage 250, for example, in a single physicalmemory device, and in other cases, memory 220 and/or storage 250 arefunctionally distributed across many physical devices. In the case ofvirtual machines or hypervisors, all or part of a function may beprovided in the form of software or firmware running over avirtualization layer to provide the disclosed logical function. In otherexamples, a device such as a network interface 260 may provide only theminimum hardware interfaces necessary to perform its logical operation,and may rely on a software driver to provide additional necessary logic.Thus, each logical block disclosed herein is broadly intended to includeone or more logic elements configured and operable for providing thedisclosed logical operation of that block. As used throughout thisspecification, “logic elements” may include hardware, external hardware(digital, analog, or mixed-signal), software, reciprocating software,services, drivers, interfaces, components, modules, algorithms, sensors,components, firmware, microcode, programmable logic, or objects that cancoordinate to achieve a logical operation.

In an example, processor 210 is communicatively coupled to memory 220via memory bus 270-3, which may be for example a direct memory access(DMA) bus by way of example, though other memory architectures arepossible, including ones in which memory 220 communicates with processor210 via system bus 270-1 or some other bus. Processor 210 may becommunicatively coupled to other devices via a system bus 270-1. As usedthroughout this specification, a “bus” includes any wired or wirelessinterconnection line, network, connection, bundle, single bus, multiplebuses, crossbar network, single-stage network, multistage network orother conduction medium operable to carry data, signals, or powerbetween parts of a computing device, or between computing devices. Itshould be noted that these uses are disclosed by way of non-limitingexample only, and that some embodiments may omit one or more of theforegoing buses, while others may employ additional or different buses.

In various examples, a “processor” may include any combination of logicelements operable to execute instructions, whether loaded from memory,or implemented directly in hardware, including by way of non-limitingexample a microprocessor, digital signal processor, field-programmablegate array, graphics processing unit, programmable logic array,application-specific integrated circuit, or virtual machine processor.In certain architectures, a multi-core processor may be provided, inwhich case processor 210 may be treated as only one core of a multi-coreprocessor, or may be treated as the entire multi-core processor, asappropriate. In some embodiments, one or more co-processor may also beprovided for specialized or support functions.

Processor 210 may be connected to memory 220 in a DMA configuration viaDMA bus 270-3 (or other similar memory interconnect). To simplify thisdisclosure, memory 220 is disclosed as a single logical block, but in aphysical embodiment may include one or more blocks of any suitablevolatile or non-volatile memory technology or technologies, includingfor example DDR RAM, SRAM, DRAM, cache, L1 or L2 memory, on-chip memory,registers, flash, ROM, optical media, virtual memory regions, magneticor tape memory, or similar. In certain embodiments, memory 220 maycomprise a relatively low-latency volatile main memory, while storage250 may comprise a relatively higher-latency non-volatile memory.However, memory 220 and storage 250 need not be physically separatedevices, and in some examples may represent simply a logical separationof function. It should also be noted that although DMA is disclosed byway of non-limiting example, DMA is not the only protocol consistentwith this specification, and that other memory architectures areavailable.

Storage 250 may be any species of memory 220, or may be a separatedevice. Storage 250 may include one or more non-transitorycomputer-readable mediums, including by way of non-limiting example, ahard drive, solid-state drive, external storage, redundant array ofindependent disks (RAID), network-attached storage, optical storage,tape drive, backup system, cloud storage, or any combination of theforegoing. Storage 250 may be, or may include therein, a database ordatabases or data stored in other configurations, and may include astored copy of operational software such as operating system 222 andsoftware portions of client agent 224. Many other configurations arealso possible, and are intended to be encompassed within the broad scopeof this specification.

Network interface 260 may be provided to communicatively couple clientdevice 200 to a wired or wireless network, and may be a networkinterface card (NIC), host fabric interface (HFI), or any other suitabledevice. A “network,” as used throughout this specification, may includeany communicative platform operable to exchange data or informationwithin or between computing devices, including by way of non-limitingexample, an ad-hoc local network, an internet architecture providingcomputing devices with the ability to electronically interact, a plainold telephone system (POTS), which computing devices could use toperform transactions in which they may be assisted by human operators orin which they may manually key data into a telephone or other suitableelectronic equipment, any packet data network (PDN) offering acommunications interface or exchange between any two nodes in a system,or any local area network (LAN), metropolitan area network (MAN), widearea network (WAN), wireless local area network (WLAN), virtual privatenetwork (VPN), intranet, or any other appropriate architecture or systemthat facilitates communications in a network or telephonic environment.

Client agent 224, in one example, is operable to carry outcomputer-implemented methods as described in this specification. Clientagent 224 may include one or more tangible non-transitorycomputer-readable mediums having stored thereon executable instructionsoperable to instruct a processor to provide a client agent 224. As usedthroughout this specification, an “engine” includes any combination ofone or more logic elements, of similar or dissimilar species, operablefor and configured to perform one or more methods provided by theengine. Thus, client agent 224 may comprise one or more logic elementsconfigured to provide methods as disclosed in this specification. Insome cases, client agent 224 may include a special integrated circuitdesigned to carry out a method or a part thereof, and may also includesoftware instructions operable to instruct a processor to perform themethod. In some cases, client agent 224 may run as a “daemon” process. A“daemon” may include any program or series of executable instructions,whether implemented in hardware, software, firmware, or any combinationthereof, that runs as a background process, aterminate-and-stay-resident program, a service, system extension,control panel, bootup procedure, BIOS subroutine, or any similar programthat operates without direct user interaction. In certain embodiments,daemon processes may run with elevated privileges in a “driver space,”or in ring 0, 1, or 2 in a protection ring architecture. It should alsobe noted that client agent 224 may also include other hardware andsoftware, including configuration files, registry entries, andinteractive or user-mode software by way of non-limiting example.

In one example, client agent 224 includes executable instructions storedon a non-transitory medium operable to perform a method according tothis specification. At an appropriate time, such as upon booting clientdevice 200 or upon a command from operating system 222 or a user 120,processor 210 may retrieve a copy of the instructions from storage 250and load it into memory 220. Processor 210 may then iteratively executethe instructions of client agent 224 to provide the desired method.

Client agent 224 may provide an interface and services for an end user,such as corporate user 120 or customer 160 to access services providedby a server 300. For example, client agent 224 may be or comprise a webbrowser, and e-mail client, or a client for a program such as filetransfer protocol (FTP), telnet, secure shell (SSH), network timeprotocol (NTP), or any other suitable network-based program.

Peripheral interface 240 may be configured to interface with anyauxiliary device that connects to client device 200 but that is notnecessarily a part of the core architecture of client device 200. Aperipheral may be operable to provide extended functionality to clientdevice 200, and may or may not be wholly dependent on client device 200.In some cases, a peripheral may be a computing device in its own right.Peripherals may include input and output devices such as displays,terminals, printers, keyboards, mice, modems, data ports (e.g., serial,parallel, USB, Firewire, or similar), network controllers, opticalmedia, external storage, sensors, transducers, actuators, controllers,data acquisition buses, cameras, microphones, speakers, or externalstorage by way of non-limiting example.

In one example, peripherals include display adapter 242, audio driver244, and input/output (I/O) driver 246. Display adapter 242 may beconfigured to provide a human-readable visual output, such as acommand-line interface (CLI) or graphical desktop such as MicrosoftWindows, Apple OSX desktop, or a Unix/Linux X Window System-baseddesktop. Display adapter 242 may provide output in any suitable format,such as a coaxial output, composite video, component video, VGA, ordigital outputs such as DVI or HDMI, by way of nonlimiting example. Insome examples, display adapter 242 may include a hardware graphics card,which may have its own memory and its own graphics processing unit(GPU). Audio driver 244 may provide an interface for audible sounds, andmay include in some examples a hardware sound card. Sound output may beprovided in analog (such as a 3.5 mm stereo jack), component (“RCA”)stereo, or in a digital audio format such as S/PDIF, AES3, AES47, HDMI,USB, Bluetooth or Wi-Fi audio, by way of non-limiting example.

FIG. 3 is a block diagram of a server-class device 300 according to oneor more examples of the present specification. Server 300 may be anysuitable computing device or apparatus, as described in connection withFIG. 2. In general, the definitions and examples of FIG. 2 may beconsidered as equally applicable to FIG. 3, unless specifically statedotherwise. Server 300 is described herein separately to illustrate thatin certain embodiments, logical operations according to thisspecification may be divided along a client-server model, wherein clientdevice 200 provides certain localized tasks, while server 300 providescertain other centralized tasks. In contemporary practice, server 300 ismore likely than client device 200 to be provided as a “headless” VMrunning on a computing cluster, or as a standalone appliance, thoughthese configurations are not required.

Server 300 includes processor 310, which may include multiple cores, andwhich may be connected to a memory 320, having stored therein executableinstructions for providing an operating system 322 and at least softwareportions of a server engine 324. Other components of server 300 includea storage 350, and network interface 360. As described in FIG. 2, eachlogical block may be provided by one or more similar or dissimilar logicelements.

In an example, processor 310 is communicatively coupled to memory 320via memory bus 370-3, which may be for example a direct memory access(DMA) bus or other suitable memory interconnect. Processor 310 may becommunicatively coupled to other devices via a system bus 370-1.

Processor 310 may be connected to memory 320 in a DMA configuration viaDMA bus 370-3, or via any other suitable memory configuration. Asdiscussed in FIG. 2, memory 320 may include one or more logic elementsof any suitable type.

Storage 350 may be any species of memory 320, or may be a separatedevice, as described in connection with storage 250 of FIG. 2. Storage350 may be, or may include therein, a database or databases or datastored in other configurations, and may include a stored copy ofoperational software such as operating system 322 and software portionsof server engine 324.

Network interface 360 may be provided to communicatively couple server140 to a wired or wireless network, and may include one or more logicelements as described in FIG. 2. Network interface 360 may be a NIC,HFI, or any other suitable device.

Server engine 324 is an engine as described in FIG. 2 and, in oneexample, includes one or more logic elements operable to carry outcomputer-implemented methods as described in this specification.Software portions of server engine 324 may run as a daemon process.

Server engine 324 may include one or more non-transitorycomputer-readable mediums having stored thereon executable instructionsoperable to instruct a processor to provide a security engine. At anappropriate time, such as upon booting server 140 or upon a command fromoperating system 322 or a user 120 or security administrator 150,processor 310 may retrieve a copy of server engine 324 (or softwareportions thereof) from storage 350 and load it into memory 320.Processor 310 may then iteratively execute the instructions of serverengine 324 to provide the desired method.

Server engine 324 may be any suitable server program, including adaemon, for providing a network-based service. These could include, byway of nonlimiting example, an HTTP or web server, an e-mail server, anFTP server, telnet server, SSH server, NTP server, or any other suitableserver. In certain embodiments, server engine 324 is the “application”of ALNQ as described herein. In certain embodiments, server engine 324may perform the method of FIG. 8 or related methods.

A queuing engine 326 may also be provided, and may be an engine asdescribed herein. Queuing engine 326 may be configured to provide ALNQqueuing services, including performing the method of FIG. 7 or relatedmethods.

FIG. 4 is a block diagram of selected elements of a server 300 accordingto one or more examples of the present specification. In this example,NIC 360 connects server 300 to network 170, which in its turn iscommunicatively coupled to a plurality of end users devices 462. Theremay be many end-user devices 462, including thousands or more ofend-user devices 462. End-user devices 462 access server 300 for thepurpose of accessing services provided by server 300, such as via serverengine 324 or any other appropriate application.

In this example, server 300 includes eight cores 310. Each core 310 maybe dedicated to a different service or thread of a service asappropriate, though that is a nonlimiting example only, and it is alsopossible for processors 310 to share different processes. In thisexample, a web server 420 is provided. Web server 420 is divided intofour separate threads. Specifically, web 0 420-0 runs on core 0 310-0.Web 1 420-1 runs on core 1 310-1. Web 2 420-2 runs on core 2 310-2. Web3 420-3 runs on core 3 310-3.

An email server 430 is also provided. In this example, two cores arededicated to email server 430. Specifically, email 0 430-0 runs on core4 310-4. Email 1 430-1 runs on core 5 310-5.

The last two cores are committed to support background processes.Specifically, support applications 450 run on core 6 310-6. Operatingsystem 322 runs on core 7 310-7. It should be understood that the numberof cores, the number of threads, and the distribution of threads amongthe several cores is provided by way of nonlimiting example. In otherembodiments, other configurations are possible. In some cases, a machinemay have many more cores, and many more threads. In other cases, amachine may have fewer cores and fewer threads. Any suitable combinationof cores and threads is available.

In this example, NIC 360 exposes queues 450 numbered 0 through 15.According to examples disclosed in this specification, queues 0 through3, comprising group 452, are dedicated to traffic on port 80. Queues 4and 5, comprising group 454, are dedicated to traffic on port 25. Queues6 through 15 are considered auxiliary queues, and are allocated for useby operating system 322 and support application 450.

When an incoming packet comes from network 170 to NIC 360, queuingengine 326 inspects the packet in a top-down fashion. In other words,queuing engine 326 inspect the upper layer information first. In thisexample, queuing engine 326 is specifically looking at which logicalport the packet is designated for. In an example, a packet is assignedto group 452 if and only if it is port 80 traffic. Thus, all port 80traffic is assigned to group 452, and no traffic that is not port 80traffic is assigned to group 452.

Similarly, if and only if incoming traffic is found to be email trafficon port 25, the traffic is assigned to group 454. In other words, allport 25 traffic is assigned to group 454, and no traffic that is notgroup that is not port 25 traffic is assigned to group 454.

Any traffic that is not either port 80 or port 25 is assigned to one ofthe auxiliary ports, numbered 6 through 15, according to standardassignment methods. This may include hashing or similar. This means thatweb server 420 knows that all of its traffic will appear in group 452,and that no outside traffic will appear in the group. Similarly, emailserver 430 knows that all of its traffic will appear in group 454, andthat no outside traffic will appear in the group. Conversely, operatingsystem 322 knows that those two groups are completely “owned” by theirrespective applications, so OS 322 can in appropriate circumstancescircumvent some of its usual security procedures and let thoseapplications handle their own internal security.

Assignment of traffic to auxiliary ports 6 through 15 may beaccomplished with any suitable method, including in some embodimentsprior art methods such as RSS, Flow Director, or similar. Similarly,once a packet has been assigned to either group 452 or 454, assignmentof the packet to queues within the group may be accomplished by anysuitable means, including RSS, Flow Director, or equivalent.

Advantageously, because it is known that group 453 includes only trafficon port 80 designated for web server 420, the operating system now hasthe flexibility to impose application specific policies andoptimizations directly. As an example it could pass the queues directlyto the application without having to consider security violations fromhaving traffic from other applications.

FIG. 5 is a view of an additional embodiment according to one or moreexamples of the present specification. In the example of FIG. 5, groups452 and 454 are twice as large as they are in the example of FIG. 4.This is to illustrate that while one-to-one mapping between queues andthreads is possible, n-to-one mapping is also possible, for any ngreater than 1.

In the example of FIG. 5, groups 452 and 454 both reserve two separatequeues for each thread. This illustrates the principle that web server420 and email server 430 may be relatively more important to thefunction of server 300 than support function 450 and operating system322. Thus, it may be advantageous in certain embodiments to allocateadditional queues for each thread, to avoid bottlenecks in thecommunication. Thus, in this example, queues 0 and 1 are reserved forweb server thread 420-0. Queues 2 and 3 are for web server thread 420-1.Queues 4 and 5 are for web server thread 420-2. Queues 6 and 7 are forweb server thread 420-3.

Similarly, queues 8 and 9 are for email server thread 430-0. Queues 10and 11 are for email server thread 430-1.

Finally, queues 12 through 15 are allocated for general purposes, andmay be used for support function 450 and operating system 322, includingall traffic not on port 80 or 25.

Note that the examples of FIG. 4 and FIG. 5 are a nonlimiting example ofa potential configuration. Other configurations are possible, includinga configuration in which the number of queues exactly matches the numberof cores, or where the number of queues is related to the number ofcores by a non-integer function.

FIG. 6 is a block diagram illustration of a traditional OSI networkstack model. In the traditional OSI model, the network stack includesseven layers, specifically physical layer 610, data link layer 620,network layer 630, transport layer 640, session layer 650, presentationlayer 660, and application layer 670. The OSI model is presented herefor purposes of illustration, but it should be understood that the OSImodel is a nonlimiting example only. The “internet protocol suite”(often referred to as TCP/IP) is also commonly used. TCP/IP layers maybe similar but not identical to OSI layers.

The seven layers of the OSI model are described briefly here for thepurpose of context for relevant portions of the present description. Thelayers are, in summary:

-   -   a. Physical Layer 610—The physical layer (layer 1) provides        networking hardware and transmission technologies. This layer        includes physical wires, clocks, voltages, and other physical        structures to provide the transmission of raw bits, rather than        logical data packets. Each bit stream may be grouped into code        words or symbols and converted to a physical signal that is        transmitted over a hardware transmission medium. The physical        layer provides an electrical, mechanical, and procedural        interface to the transmission medium. Within the context of the        seven-layer model, the physical layer translates logical        communications requests from the data link layer into        hardware-specific operations to effect transmission or reception        of electronic signals.    -   b. Data Link Layer 620—The data link layer (layer 2) is the        protocol layer that transfers data between adjacent network        nodes to provide functional and procedural transfer of data        between network entities. In certain embodiments, the data link        layer also provides error detection and correction. The basic        data unit at this layer is a data link frame, which is not        intended to cross a local network boundary. Routing between        networks and global addressing are performed at higher layers.        This allows the data link layer to focus on local delivery,        addressing, and media arbitration. Data-link protocols specify        how devices detect and recover from collisions, and may provide        mechanisms to reduce or prevent them. Thus, in certain existing        architectures, queuing of packets is based on using hashes of        values or absolute values available at this layer, such as a MAC        address.    -   c. Network Layer 630—Layer 3 is the network layer. The network        layer is responsible for packet forwarding, including routing        through intermediate routers. The network layer provides the        functional and procedural means of transferring variable-length        data sequences from a source to a destination host via one or        more networks, while maintaining the quality of service        functions. Functions of the network layer include:        -   i. Connection model: connectionless communication. For            example, IP is connectionless, in that a datagram can travel            from a sender to a recipient without the recipient having to            send an acknowledgement. Connection-oriented protocols exist            at other, higher layers of the OSI model.        -   ii. Host addressing. Every host in the network must have a            unique address that determines where it is. This address is            normally assigned from a hierarchical system. In TCP/IP,            this is an IP address, either 32-bit IPv4 (e.g.,            192.168.1.1), or 128-bit IPv6 (e.g.,            2001:0DB8:AC10:FE01:0000:0000:0000:0000). An IPv4 address            may be either globally unique, or locally unique (i.e., if            it is used in a local subnetwork). An IPv6 address is            intended to be globally unique.        -   iii. Message forwarding. Since many networks are partitioned            into subnetworks and connect to other networks for wide-area            communications, networks use specialized hosts, called            gateways or routers, to forward packets between networks.            This is also of interest to mobile applications, where a            user may move from one location to another, and it must be            arranged that his messages follow him.        -   iv. The network layer responds to service requests from the            transport layer and issues service requests to the data link            layer.    -   d. Transport Layer 640—Layer 4 is the transport layer, which        provides end-to-end or host-to-host communication services for        applications. The transport layer provides services such as        connection-oriented data stream support, reliability, flow        control, and multiplexing. Simple connectionless (stateless)        implementations may use user datagram protocol (UDP) at Layer 4,        while connection-oriented (stateful) implementations may use        transmission control protocol (TCP). Datagram Congestion Control        Protocol (DCCP) and Stream Control Transmission Protocol (SCTP)        are also provided by way of nonlimiting example.    -   e. Session Layer 650—Layer 5 is the session layer. The session        layer opens, closes, and manages sessions between end-user        applications, such as end-user application 162 or client        application 112 of FIG. 1 and a web server 420 of FIG. 4.        Communication sessions consist of requests and responses that        occur between applications. Session-layer services are commonly        used in application environments that make use of remote        procedure calls (RPCs). The session layer may respond to service        requests from the presentation layer and issues service requests        to the transport layer.    -   f. Presentation Layer 660—Layer 6 is the presentation layer,        also called the syntax layer. The presentation layer is        responsible for the delivery and formatting of information to        the application layer for further processing or display,        including serialization of data structures into flat byte        strings. This layer handles syntactical differences in data        representation within the end-user systems. For example,        EBCDIC-coded data may be converted to ASCII for use with an        application. This layer also handles issues of diverse data        types. For example, Pascal-style text strings, with an explicit        integer length, may need to be interpreted differently from        C-style null-terminated strings. Where appropriate, encryption        may also be performed at this layer.    -   g. Application Layer 670—Layer 7 is the application layer. In        the OSI model, layer 7 is responsible for displaying received        information to the user.

In certain existing networking architectures, incoming traffic to anetwork interface such as NIC 360, traffic is assigned to queues such asqueues 450.

FIG. 7 is a flowchart of a method 700 performed by queuing engine 326,particularly for received packets, according to one or more examples ofthe present specification.

In block 720, NIC 360 receives an incoming packet on. This means thatthe physical interface receives electrical signals providing an incomingdata packet.

In block 730, queuing engine 326 parses the packet in a top-down manner.Specifically, in this example, queuing engine 326 extracts thedestination port for the packet, though other values may be used.

In block 740, queuing engine 326 determines whether the port isconfigured a “listening” port. If so, it identifies a number of queuesin the group allocated for this port.

Block 750, queuing engine 326 load balances or distributes the packet toits assigned queue. For example, if group 452 has been designated forHTTP traffic, and if the incoming packet is on port 80, then queuingengine 326 may assign the packet to one of the cues in group 452according to an appropriate load-balancing algorithm. RSS, FlowDirector, or similar may be used to identify the specific queue toassign the packet into. The packet may then be made available via directmemory access (DMA), so that it can be accessed independently of theprocessor where appropriate.

In block 760, if interrupts are enabled (e.g., rather than “busypolling,”) and the interrupt throttling timer has expired, queuingengine 326 sends an interrupt to the host. In other words, the interruptdriver does not trigger an interrupt with every incoming packet. Rather,interrupts are triggered only when a threshold of packets or time hasbeen reached. An interrupt service routine may then signal server engine324 directly. Interrupts are asserted depending on the triggering logic,and if asserted signal the application. In either case, polling fromserver engine 324 may trigger the packet flow.

In block 780, queuing engine 326 sends a queuing notification to theappropriate process, such as a thread of server engine 324. For example,in the case of web server 420, queuing engine 326 may send anotification to the appropriate thread such as thread 0 420-0 of theprocess. Specifically, the driver may pick the packet from the queue,and pass along with the packet, opaque information that identified thespecific queue. This information is stored in the sockets layer andavailable to the application.

In block 799, the method is done.

FIG. 8 is a flowchart of a method 800 performed by an application, suchas server engine 324, according to one or more examples of the presentspecification.

In block 810, the application thread makes and asynchronous poll call.For example the Linux operating system provides a call known as EPOLL.If using EPOLL or similar, the application gets the opaque queueidentifier for the socket it is watching for and checks to see if thatit matches the queue identifier for other sockets it is watching for aparticular event file descriptor. If so, it adds this socket to thewatch list. Otherwise, it hands the socket to the event file descriptorthat has the matching queue identifier and is added to its watch list.In an example, a single thread operates on a single event filedescriptor. Thus, creating the match of watching sockets with the samequeue identifier streamlines the traffic flow without interference fromother applications.

In block 820, the application thread polls its assigned queues accordingto the socket/event file descriptors provided by asynchronous polling.If the thread was asleep because there is no data (and consequently, nowork for it do), a wakeup may be performed directly on the sleepingthread, allowing the thread to come back and pull packets from itsqueues. In other words, protocol and descriptor processing occur in thecontext of the thread, not in the context of the interrupt, or deferredprocedure call (DPC) (Windows)/SoftIRQ (Linux), which is scheduled as aresult of an interrupt. In doing so, scheduling affinities arepreserved. The scheduler wakeup of the application (such as serverengine 326) keeps all shared kernel data structures associated withpacket delivery and transmission in the same caching/scheduling domain,aligning with the scheduling policies of an operating system/hypervisor.

In block 830, the application thread performs busy pulling until thereis a timeout. Busy polling sockets may be streamlined to pull packetsdirectly from the application-specific queues.

In decision block 840, if data are available, then in block 870, method900 of FIG. 9 is performed.

If data are not available, then in block 880, the thread goes to sleepwith interrupts enabled.

In block 899, the method is done.

FIG. 9 is a flowchart of a method 900 disclosing additional details ofdata consumption according to one or more examples of the presentspecification.

In block 940, NIC 360 stamps a queue identifier token associated with apacket, and propagates the identifier up the network stack. Application324 then receives the queue identifier from NIC 360. Note that if thereis more than one NIC 360, this may also include a device identifier (forexample, NIC 0, queue 1; NIC 1, queue 1; etc).

In block 960, the socket layer stores the queue identifier as part ofits state. Again, the queue identifier may be device specific.

In block 980, application 324 consumes the data.

In block 999, the method is done.

FIG. 10 is a flow chart of a method 1000 of performing a transmitoperation with ALNQ according to one or more examples of the presentspecification. This method is understood as a nonlimiting example, andin particular, specific network layers are assigned operations in thisflow chart by way of illustration.

In block 1010, application 324 may set queue mapping for the socket,such as via extended socket options. Note that this may be necessaryonly if the send-to queue is different from the last transmit operation.

In block 1030, application 324 sends the packet using the normal socketSEND call.

In block 1040, the socket layer of the network stack appends the queueidentifier to the sent packet.

In block 1050, the protocol and network layers perform their normal,known functions.

In block 1060, the device layer checks the queue identifier and placesthe packet on a specified queue for transmission.

In block 1080, the device layer signals the appropriate NIC 360 that thepacket is ready for transmission.

In block 1090, NIC 360 transmits the packet.

In block 1099, the method is done.

The foregoing outlines features of several embodiments so that thoseskilled in the art may better understand various aspects of the presentdisclosure. Those skilled in the art should appreciate that they mayreadily use the present disclosure as a basis for designing or modifyingother processes and structures for carrying out the same purposes and/orachieving the same advantages of the embodiments introduced herein.Those skilled in the art should also realize that such equivalentconstructions do not depart from the spirit and scope of the presentdisclosure, and that they may make various changes, substitutions, andalterations herein without departing from the spirit and scope of thepresent disclosure. Note that client device 200 and server 300 may bothbe examples of computing apparatuses or other computing devices.

All or part of any hardware element disclosed herein may readily beprovided in a system-on-a-chip (SoC), including central processing unit(CPU) package. An SoC represents an integrated circuit (IC) thatintegrates components of a computer or other electronic system into asingle chip. Thus, for example, client devices 110 or server devices 300may be provided, in whole or in part, in an SoC. The SoC may containdigital, analog, mixed-signal, and radio frequency functions, all ofwhich may be provided on a single chip substrate. Other embodiments mayinclude a multi-chip-module (MCM), with a plurality of chips locatedwithin a single electronic package and configured to interact closelywith each other through the electronic package. In various otherembodiments, the computing functionalities disclosed herein may beimplemented in one or more silicon cores in Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), andother semiconductor chips.

Note also that in certain embodiment, some of the components may beomitted or consolidated. In a general sense, the arrangements depictedin the figures may be more logical in their representations, whereas aphysical architecture may include various permutations, combinations,and/or hybrids of these elements. It is imperative to note thatcountless possible design configurations can be used to achieve theoperational objectives outlined herein. Accordingly, the associatedinfrastructure has a myriad of substitute arrangements, design choices,device possibilities, hardware configurations, software implementations,and equipment options.

In a general sense, any suitably-configured processor, such as processor310, can execute any type of instructions associated with the data toachieve the operations detailed herein. Any processor disclosed hereincould transform an element or an article (for example, data) from onestate or thing to another state or thing. In another example, someactivities outlined herein may be implemented with fixed logic orprogrammable logic (for example, software and/or computer instructionsexecuted by a processor) and the elements identified herein could besome type of a programmable processor, programmable digital logic (forexample, a field programmable gate array (FPGA), an erasableprogrammable read only memory (EPROM), an electrically erasableprogrammable read only memory (EEPROM)), an ASIC that includes digitallogic, software, code, electronic instructions, flash memory, opticaldisks, CD-ROMs, DVD ROMs, magnetic or optical cards, other types ofmachine-readable mediums suitable for storing electronic instructions,or any suitable combination thereof.

In operation, a storage such as storage 350 may store information in anysuitable type of tangible, non-transitory storage medium (for example,random access memory (RAM), read only memory (ROM), field programmablegate array (FPGA), erasable programmable read only memory (EPROM),electrically erasable programmable ROM (EEPROM), etc.), software,hardware (for example, processor instructions or microcode), or in anyother suitable component, device, element, or object where appropriateand based on particular needs. Furthermore, the information beingtracked, sent, received, or stored in a processor could be provided inany database, register, table, cache, queue, control list, or storagestructure, based on particular needs and implementations, all of whichcould be referenced in any suitable timeframe. Any of the memory orstorage elements disclosed herein, such as memory 320 and storage 350,should be construed as being encompassed within the broad terms ‘memory’and ‘storage,’ as appropriate. A non-transitory storage medium herein isexpressly intended to include any non-transitory special-purpose orprogrammable hardware configured to provide the disclosed operations, orto cause a processor such as processor 310 to perform the disclosedoperations.

Computer program logic implementing all or part of the functionalitydescribed herein is embodied in various forms, including, but in no waylimited to, a source code form, a computer executable form, machineinstructions or microcode, programmable hardware, and variousintermediate forms (for example, forms generated by an assembler,compiler, linker, or locator). In an example, source code includes aseries of computer program instructions implemented in variousprogramming languages, such as an object code, an assembly language, ora high-level language such as OpenCL, Fortran, C, C++, JAVA, or HTML foruse with various operating systems or operating environments, or inhardware description languages such as Spice, Verilog, and VHDL. Thesource code may define and use various data structures and communicationmessages. The source code may be in a computer executable form (e.g.,via an interpreter), or the source code may be converted (e.g., via atranslator, assembler, or compiler) into a computer executable form, orconverted to an intermediate form such as byte code. Where appropriate,any of the foregoing may be used to build or describe appropriatediscrete or integrated circuits, whether sequential, combinatorial,state machines, or otherwise.

In one example embodiment, any number of electrical circuits of theFIGURES may be implemented on a board of an associated electronicdevice. The board can be a general circuit board that can hold variouscomponents of the internal electronic system of the electronic deviceand, further, provide connectors for other peripherals. Morespecifically, the board can provide the electrical connections by whichthe other components of the system can communicate electrically. Anysuitable processor and memory can be suitably coupled to the board basedon particular configuration needs, processing demands, and computingdesigns. Other components such as external storage, additional sensors,controllers for audio/video display, and peripheral devices may beattached to the board as plug-in cards, via cables, or integrated intothe board itself. In another example, the electrical circuits of theFIGURES may be implemented as stand-alone modules (e.g., a device withassociated components and circuitry configured to perform a specificapplication or function) or implemented as plug-in modules intoapplication specific hardware of electronic devices.

Note that with the numerous examples provided herein, interaction may bedescribed in terms of two, three, four, or more electrical components.However, this has been done for purposes of clarity and example only. Itshould be appreciated that the system can be consolidated orreconfigured in any suitable manner. Along similar design alternatives,any of the illustrated components, modules, and elements of the FIGURESmay be combined in various possible configurations, all of which arewithin the broad scope of this specification. In certain cases, it maybe easier to describe one or more of the functionalities of a given setof flows by only referencing a limited number of electrical elements. Itshould be appreciated that the electrical circuits of the FIGURES andits teachings are readily scalable and can accommodate a large number ofcomponents, as well as more complicated/sophisticated arrangements andconfigurations. Accordingly, the examples provided should not limit thescope or inhibit the broad teachings of the electrical circuits aspotentially applied to a myriad of other architectures.

Numerous other changes, substitutions, variations, alterations, andmodifications may be ascertained to one skilled in the art and it isintended that the present disclosure encompass all such changes,substitutions, variations, alterations, and modifications as fallingwithin the scope of the appended claims. In order to assist the UnitedStates Patent and Trademark Office (USPTO) and, additionally, anyreaders of any patent issued on this application in interpreting theclaims appended hereto, Applicant wishes to note that the Applicant: (a)does not intend any of the appended claims to invoke paragraph six (6)of 35 U.S.C. section 112 (pre-AIA) or paragraph (f) of the same section(post-AIA), as it exists on the date of the filing hereof unless thewords “means for” or “steps for” are specifically used in the particularclaims; and (b) does not intend, by any statement in the specification,to limit this disclosure in any way that is not otherwise expresslyreflected in the appended claims.

Example Implementations

There is disclosed in one example a network interface card (NIC),comprising: an ingress interface to receive incoming traffic; aplurality of queues to queue incoming traffic; an egress interface todirect incoming traffic to a plurality of server applications; and aqueuing engine, including logic to: uniquely associate a queue with aselected server application; receive an incoming network packet;determine that the selected server application may process the incomingnetwork packet; and assign the incoming network packet to the queue.

There is further disclosed an example NIC, wherein determining that theselected server application may process the incoming network packetcomprises inspecting an application identifier of the incoming networkpacket.

There is further disclosed an example NIC, wherein the applicationidentifier comprises a port number.

There is further disclosed an example NIC, further comprising means fornotifying the selected server application of the assigning.

There is further disclosed an example NIC, further comprising means toenable the selected server application to bypass an interrupt mechanismand to perform per-thread, non-interfering busy polling.

There is further disclosed an example NIC, wherein the queuing engine isfurther to receive a queue mapping for a socket via an extended socketoption.

There is further disclosed an example NIC, wherein the queueing enginefurther includes logic to uniquely associate a plurality of queues withthe selected server application.

There is further disclosed an example NIC, wherein the queueing enginefurther includes logic to uniquely assign a second queue to a secondselected server application.

There is further disclosed an example NIC, wherein the queueing enginefurther includes logic to assign a support queue to handle incomingpackets not directed to a queue uniquely assigned to a serverapplication.

There is further disclosed an example NIC, wherein the queueing enginefurther includes logic to assign a plurality of support queues.

There is further disclosed an example NIC, wherein the plurality ofsupport queues number less than a sum of queues uniquely assigned to oneor more selected server applications.

There is also disclosed in one example a tangible, non-transitorystorage medium having stored thereon instructions to instruct a networkinterface card (NIC) to: deterministically associate an ingress queue ofthe NIC with a server function to be serviced by the NIC; receive anincoming network packet on an ingress interface of the NIC; determinethat the server function may process the incoming network packet; andassign the incoming network packet to the queue.

There is further disclosed an example of a tangible, non-transitorystorage medium, wherein determining that the selected server applicationmay process the incoming network packet comprises inspecting anapplication identifier of the incoming network packet.

There is further disclosed an example of a tangible, non-transitorystorage medium, wherein the application identifier comprises a portnumber.

There is further disclosed an example of a tangible, non-transitorystorage medium, wherein the queueing engine further includes logic touniquely associate a plurality of queues with the selected serverapplication.

There is further disclosed an example of a tangible, non-transitorystorage medium, wherein the queueing engine further includes logic touniquely assign a second queue to a second selected server application.

There is further disclosed an example of a tangible, non-transitorystorage medium, wherein the queueing engine further includes logic toassign a support queue to handle incoming packets not directed to aqueue uniquely assigned to a server application.

There is also disclosed an example method of providing deterministicper-application packet queueing, comprising: uniquely associating one ormore ingress queues of a network interface card (NIC) with a serverfunction to be serviced by the NIC; receiving an incoming network packeton an ingress interface of the NIC; determining that the network packetis directed to the associated server function; and assigning theincoming network packet to a queue selected from the one or moreuniquely associated queues.

There is further disclosed an example method, wherein determining thatthe network packet is directed to the associated server functioncomprises inspecting an application identifier of the incoming networkpacket.

There is further disclosed an example method, wherein the applicationidentifier comprises a port number.

What is claimed is:
 1. A network interface card (NIC), comprising: aningress interface to receive incoming traffic; a plurality of queues toqueue incoming traffic; an egress interface to direct incoming trafficto a plurality of server applications; and a queuing engine, includinglogic to: uniquely associate a queue with a selected server application;receive an incoming network packet; determine that the selected serverapplication may process the incoming network packet; and assign theincoming network packet to the queue.
 2. The NIC of claim 1, whereindetermining that the selected server application may process theincoming network packet comprises inspecting an application identifierof the incoming network packet.
 3. The NIC of claim 2, wherein theapplication identifier comprises a port number.
 4. The NIC of claim 1,further comprising means for notifying the selected server applicationof the assigning.
 5. The NIC of claim 1, further comprising means toenable the selected server application to bypass an interrupt mechanismand to perform per-thread, non-interfering busy polling.
 6. The NIC ofclaim 1, wherein the queuing engine is further to receive a queuemapping for a socket via an extended socket option.
 7. The NIC of claim1, wherein the queueing engine further includes logic to uniquelyassociate a plurality of queues with the selected server application. 8.The NIC of claim 1, wherein the queueing engine further includes logicto uniquely assign a second queue to a second selected serverapplication.
 9. The NIC of claim 1, wherein the queueing engine furtherincludes logic to assign a support queue to handle incoming packets notdirected to a queue uniquely assigned to a server application.
 10. TheNIC of claim 9, wherein the queueing engine further includes logic toassign a plurality of support queues.
 11. The NIC of claim 10, whereinthe plurality of support queues number less than a sum of queuesuniquely assigned to one or more selected server applications.
 12. Atangible, non-transitory storage medium having stored thereoninstructions to instruct a network interface card (NIC) to:deterministically associate an ingress queue of the NIC with a serverfunction to be serviced by the NIC; receive an incoming network packeton an ingress interface of the NIC; determine that the server functionmay process the incoming network packet; and assign the incoming networkpacket to the queue.
 13. The tangible, non-transitory storage medium ofclaim 12, wherein determining that the selected server application mayprocess the incoming network packet comprises inspecting an applicationidentifier of the incoming network packet.
 14. The tangible,non-transitory storage medium of claim 13, wherein the applicationidentifier comprises a port number.
 15. The tangible, non-transitorystorage medium of claim 12, wherein the queueing engine further includeslogic to uniquely associate a plurality of queues with the selectedserver application.
 16. The tangible, non-transitory storage medium ofclaim 12, wherein the queueing engine further includes logic to uniquelyassign a second queue to a second selected server application.
 17. Thetangible, non-transitory storage medium of claim 12, wherein thequeueing engine further includes logic to assign a support queue tohandle incoming packets not directed to a queue uniquely assigned to aserver application.
 18. A method of providing deterministicper-application packet queueing, comprising: uniquely associating one ormore ingress queues of a network interface card (NIC) with a serverfunction to be serviced by the NIC; receiving an incoming network packeton an ingress interface of the NIC; determining that the network packetis directed to the associated server function; and assigning theincoming network packet to a queue selected from the one or moreuniquely associated queues.
 19. The method of claim 18, whereindetermining that the network packet is directed to the associated serverfunction comprises inspecting an application identifier of the incomingnetwork packet.
 20. The method of claim 19, wherein the applicationidentifier comprises a port number.